1 link tagged with all of: mcp + code mode + programmatic tool calling + tool calling + agents
Click any tag below to further narrow down your results
Links
The article argues that agent harnesses are collapsing large tool catalogs into a single exec(code) tool, where the model writes a script that chains actions in a sandbox instead of calling tools one turn at a time. It covers why this helps and what it changes about how tools need to be designed.
- Standard tool calling is one action per turn, so chained workflows burn round-trips and context; Code Mode lets the model script dependent steps, loops, and parallel calls in one pass.
- Only the final summary returns to the context window; intermediate payloads stay in the sandbox, which the author ties to context savings and cost reductions (Factory reported a 15% drop in model spend and a +3.5 point Terminal-Bench gain after switching Droid to Code Mode).
- Typed interfaces, a credential and policy bridge, and persistent state outside the prompt make a JS or Python sandbox more practical than bash, though existing CLIs and skills may need rework to fit.